About the Content Package Conformance Test

	*About the Content Package Conformance Test*

The following is an excerpt from the ADL SCORM Version 1.2 Conformance Matrix that is covered by the Content Package Conformance Test

Content Package (Resource Package and Content Aggregation Package)
Conformance Category	Conformance Label	Requirements Summary
SCORM Content Packaging XML Conformant	ADLCP-PIF1	The Content Package: If the Content Package is contained in a Package Interchange File (PIF), the PIF shall be compatible with PKZIP Version 2.04g, and The Manifest shall be placed at the root of the Package (e.g. ZIP archive or CD-ROM), and The Manifest shall be named "imsmanifest.xml", and All supporting control documents shall be placed at the root of the PIF or root directory, and The "imsmanifest.xml" shall be well-formed XML, and The "imsmanifest.xml" shall validate against the IMS Content Packaging XML Schema Definition (XSD) Version 1.1.2, and The "imsmanifest.xml" shall validate against the ADL Content Packaging XML Schema Definition (XSD) Version 1.2, and The Content Package shall contain at least on Sharable Content Object or Asset as defined in the SCORM Content Aggregation Model, and All Sharable Content Object (SCO) learning resources identified in the "imsmanifest.xml" shall be at a minimum: SCO-RTE1, and All Meta-data used with the "imsmanifest.xml" shall adhere to the appropriate SCORM Meta-data Application Profile requirements.

Complete Conformance Matrix

The Content Package Conformance Test verifies that the tested Content Package is conformant the Content Aggregation Model of the SCORM®.

The purpose of this test is to verify that the test subject:

Contains an imsmanifest XML document at the root of the Package Interchange File (PIF) that:

Is well-formed;
Validates against the ADL Content Packaging Version 1.2 Schema;
Implements all mandatory elements correctly;
Uses optional elements and if they are used, then they are used correctly;
Uses extensions.

Contains conformant Asset, SCO, Content Aggregation, and Package Meta-data as determined by the Meta-data Conformance Test
Contains conformant SCOs as determined by the Sharable Content Object Run-Time Environment Test

The following will be tested for each element, where applicable:

Correct use of repeating elements (i.e. multiplicity).
- An ERROR will be logged for any mandatory element that is not used
- An ERROR will be logged for any element exceeding one (1) instance for those with a multiplicity of "0 or 1" or "1 and only 1" (Note: This causes XML validation errors)
Adherence to "restricted vocabularies"
- An ERROR will be logged for any element that is not part of the restricted vocabulary list
Adherence to the smallest permitted maximum number of characters
- An WARNING will be logged for any element that exceeds the smallest permitted maximum number of characters allowed
Correct use of Timespan data types
- A ERROR will be logged for any element with a Timespan data type that does not adhere to the format (hhhh:mm:ss.ss) as specified in the SCORM Content Packaging Information Model and XML Binding
Correct use of IDRef data types
- A ERROR will be logged for any element with an IDRef data type that does not reference an existing ID
Correct use of ID data types
- A ERROR will be logged for any element with an ID data type that is not unique within the manifest
Correct use of location/href
- A ERROR will be logged for any element with an href attribute or location that does not reference an existing File or URL

Note: Warnings do not determine conformance. These are only suggested conventions. However, using these suggestions ensure the greatest interoperability.

Test Notes

The test can be run on a single Package Interchange File (PIF) or a single imsmanifest.xml file.

Note: At this point in time it is necessary to copy all required Schemas (.xsd files) to the Desktop due to the XML parser that is being utilized.

The first series of prompts ask for information about the product being tested. You may click continue without entering any information at this prompt if you wish.
Select the type of test to be performed by pressing the appropriate radio button. You can test a stand-alone manifest XML document, a Package Interchange File in the form of a PKZIP 2.0.4 (or compatible), or an uncompressed Package Interchange File (on CD-ROM for example). Note: Conformance cannot be achieved if you choose to run a stand-alone manifest XML document.
Select the type of ADL Package to be tested (i.e., Content Aggregation Package or Resource Package) by pressing the appropriate radio button.
Press the "Browse" button to select the manifest or PIF zip file that is to be tested.
Once the "Begin Test" button is pressed the Test Suite will test the manifest and any referenced or in-line meta-data for conformance.
Any SCOs found in the Package will be tested after the manifest test is complete. If any SCOs were found in the Package, the test will continue with steps 4 - 6. Otherwise, testing is complete at step 3.
- Enter a timeout period (default is 20 seconds). This is the number of seconds the Test Suite will wait for a LMSInitialize(""). If the call is not made within this time, the Test Suite will end and the SCO will be deemed Non-Conformant.
  Note: If there is a possibility that the SCO may not call LMSInitialize("") in the first 20 seconds, this default value will need to be changed. No warning or error will be logged for changing this value.
- Optionally, you may enter initialization values for any of the following elements: Student ID, Student Name, credit/no-credit, Lesson Mode, or Launch Data. (These values are typically defaults that are provided by the LMS or via a Manifest.) Click the "Continue" button to continue
- Click the "Launch SCO" button to launch the first SCO for testing.
- After the first SCO has completed testing, click the "Complete Test" button to quit that SCOs test
- Any following SCOs will be launched and tested once the "OK" button is clicked on the pop-up window.
- The "Abort Test" button should be used if a call to LMSFinish("") is not received from the SCO being tested. The tester should wait for a period of time to see if the call will be invoked. If not, the "Abort Test" button will send a call to LMSFinish("") and end the testing, marking the SCO as being Non-Conformant
Please Note: Summary information about the actions being performed and their outcomes will be written to the Summary Log. The details of the test will be written to the Detail Log, which can be viewed by clicking on the link presented in the Summary Log. You will be able to view any errors that may be encountered, as well as the step- by-step progression of the test through the Summary and Detailed Logs.
Print Log: This link has been removed from the log frame. Note: Printing can be accomplished by right-clicking in the log frame and choosing print. This will only print the summary log. If you want to print the detailed log, each link will need to be explored and printed using the browsers print feature.
Save Log: Clicking on this link will cause a "Save As" dialog box to appear. This allows the Tester to save the ADL SCORM Conformance Test Suite Log. Please, only provide a filename; The extension is fixed as ".htm". Note: The "Save Log" functionality saves the summary log only. The Detailed Log Folder is automatically saved in following directory: <drive>:<\install_dir>\testsuite\contentpackage\tempdir\Log_<timestamp>
Add Comments. Clicking on this link will cause a window to pop up to allow the tester to add comments to the Test Suite Log
Log Legend. Clicking on this link will cause a window to pop up describing the logs colors and icons